Skip to content

Add anchors to policy sub-sections #2049

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add anchors to policy sub-sections #2049

wants to merge 1 commit into from

Conversation

dotproto
Copy link
Collaborator

This PR addresses a long standing frustration of mine: it's not possible to link developers directly to a sub-section of the add-ons policies. To address this, I've manually hacked in <span> tags with ID attributes to the H3 and H4 elements on the policies page.

Ideally we would have a more robust way of generating header anchors but for now this is better than nothing.

@dotproto dotproto requested a review from rebloor April 10, 2025 18:32
@@ -45,7 +46,7 @@ When an add-on is given human review or otherwise assessed by Mozilla, these pol

Users should be able to easily discern the functionality of your add-on based on the listing, and should not be presented with unexpected user experiences after installing it. The listing should include an easy-to-read description of what the add-on does, and what information it collects. Please consult our best practices guide for [creating an appealing listing](/documentation/develop/create-an-appealing-listing/).

### Unexpected features
### <span id="unexpected-features"></span>Unexpected features
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dotproto I assume you've tested and these work as expected? I ask, as it appears that the "correct" way of doing this would be like this, as per develop.md:

<section id="user-experience" class="page-section-container">

<!-- Single Column Body Module -->

{% capture content %}

## User Experience

{% endcapture %}
{% include modules/one-column.liquid,
	content: content
%}

<!-- END: Single Column Body Module -->

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants